-
Notifications
You must be signed in to change notification settings - Fork 0
[minor] drop 3.9 in favour of 3.13 #36
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Coverage summary from CodacySee diff coverage on Codacy
Coverage variation details
Coverage variation is the difference between the coverage for the head and common ancestor commits of the pull request branch: Diff coverage details
Diff coverage is the percentage of lines that are covered by tests out of the coverable lines that the pull request added or modified: See your quality gate settings Change summary preferences |
Pull Request Test Coverage Report for Build 13907416732Details
💛 - Coveralls |
The coveralls python package does not support Python 3.13 yet. TheKevJames/coveralls-python#549 Is it required? Or is it possible to replace it with the coveralls GitHub action https://github.com/coverallsapp/github-action |
# Conflicts: # .github/workflows/push-pull.yml
Signed-off-by: liamhuber <[email protected]>
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #36 +/- ##
=======================================
Coverage 95.00% 95.00%
=======================================
Files 13 13
Lines 560 560
=======================================
Hits 532 532
Misses 28 28 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
Ah darnit, the codacy and coveralls env files are still getting included. I was just too sloppy verifying pyiron/actions#146 and there must still be a little bug. I'll fix it tomorrow. |
Signed-off-by: liamhuber <[email protected]>
The action itself was (correctly) still maintaining the old env files by default, so in pyiron/actions#147 I just manually turned it off in the reusable workflows whenever we're not actually trying to calculate coverage. |
The coverage env issues are resolved; 3.13 alone is failing with an exception that is new to me:
|
I find this rather confusing, as it complains about the availability of setuptools.build_meta, but the head of my pyproject.toml suggests this should be available:
@jan-janssen, I peeked at executorlib for a reference, but your pyproject file looks quite similar (and identical in terms of setuptools and the build-backend), yet works fine on 3.13. Have you seen this error before? |
I didn't find anything similar on a web search; I tried re-running; I tried deleting the p3.13 cache and re-running. Unfortunately, no progress. |
@@ -1,4 +1,4 @@ | |||
channels: | |||
- conda-forge | |||
dependencies: | |||
- python >=3.9,<3.13 | |||
- python >=3.10,<3.14 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- python >=3.10,<3.14 | |
- python >=3.10,<3.14 | |
- setuptools |
@@ -7,4 +7,4 @@ dependencies: | |||
- sphinx-gallery | |||
- sphinx-rtd-theme | |||
- versioneer | |||
- python >=3.9,<3.13 | |||
- python >=3.10,<3.14 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- python >=3.10,<3.14 | |
- setuptools | |
- python >=3.10,<3.14 |
It might be just missing |
Yeah, I was just poking deeper and see setuptools is pinned in your env file |
They [were removed](https://conda-forge.org/news/2024/08/21/sunsetting-pip-deps/?utm_source=chatgpt.com) Signed-off-by: liamhuber <[email protected]>
Thank you for the pointer. I let the bot handle the changes rather than the suggestions, but this was indeed the issue. It turns out that since there are so many build tools available now conda-forge is no longer packaging setuptools and wheel by default. I'll go through the rest of the release process for snippets and then give a little report on Monday. |
Signed-off-by: liamhuber <[email protected]>
In lieu of 3.9
If the tests pass (I don't anticipate a reason they wouldn't), the support bounds can be changed accordingly